Search This CD Index Contact Us
Home > Administration > ADAP > Using the ADAP Database Modification Commands
| Using the ADAP Database Modification Commands
> ### Overview For each of the following retrieval commands, these topics provides the syntax, a description, errors, Output format, and an example.
> addrsub | changsub
> addsub | changsw
> changcex | chgrcom
> changcom | chgrext
> changcos | chgrmach
> changext | chgrnam
> changmis | delrsub
> changmsg | delsub
> changnam | setalogp
> changpwd |
> ### addrsub Add remote subscriber #### Syntax ####
> addrsub [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command adds subscribers to the current database of the voice mail system. Use the name, extension, machine, and community ID as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Input Format The input consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension/text address | C | 64
> | machine/trusted server name | C | 10
> | [community id] | N | 2
> #### Output format The Output format for each record consists of the command statistics as follows: `REMOTE SUBSCRIBER ADD ROUTINE` (<ADAP version name>) `name = ___________; extension/text address = __________; machine/trusted server name = ______; community id = ____; ____: ADDED REMOTE SUB __________` #### Example The following command adds one remote subscriber to the subscriber database. addrsub -i "Doe, John","74199","denver","1" The following data appears on the screen: `REMOTE SUBSCRIBER ADD ROUTINE` (<ADAP version name>) `name = Doe, John; extension/text address = 74199; machine/trusted server name = denver; community id = 1;` `1: ADDED REMOTE SUB 74199` ### addsub Add subscriber #### Syntax ####
> addsub [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description Adds subscribers to the current database of the voice mail system. Use the name, extension, password, class of service, switch number, and community ID as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Input Format The Input format consists of one record for each subscriber, formatted as follows.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension | K | 10
> | password | C | 15
> | [class of service] | K | 8
> | [switch number] | N | 2
> | [community id] | N | 2
> When connected to a INTUITY AUDIX system, you may use the value custom for the class of service. The service attribute values for class of service 0 are used, but the subscriber's class of service are not associated with class of service 0 (i.e. if class of service 0 changes, the subscriber's class of service does not change). #### Output Format The output for each record consists of the command statistics as follows: `SUBSCRIBER ADD ROUTINE (<ADAP version name>) name = __________; extension = _______; password = ____; cos = ____; switch number = ________; community id = _______________; ____: ADDED EXT __________` #### Example The following command adds one subscriber to the subscriber database. addsub -i "Doe, John","3501","0","0","0","1" The following data appears on the screen: `SUBSCRIBER ADD ROUTINE` (<ADAP version name>) `"Doe, John","3501","0","0","0","1" name = Doe, John; extension = 3501; password = 0; cos = 0; switch number = 0; community id = 1; 1: ADDED EXT 3501` ### changcex Change subscriber covering extension #### Syntax ####
> #### changcex [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### #### Description This command modifies subscriber covering extensions in the current database of the voice mail system. Use the name, extension, and new covering extension as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or extension does not belong to a valid system subscriber, an error message displays. If more records exist in the input, database modification continues with the next input record. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension | K | 10
> | new covering extension | K | 10
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE COVERING EXTENSION ROUTINE` (<ADAP version name>) `name = ___________; extension = _______; new covering ext. = _______;` `____: CHANGED COVERING EXT _________``_` #### Example The following command modifies one subscriber in the subscriber database. changcex -i "Martinez, Bob","73101"","73102" `The following data appears on the screen:` `CHANGE COVERING EXTENSION ROUTINE` (<ADAP version name>) `"Martinez, Bob","73101","73102" name = Martinez, Bob; extension = 73102; new covering ext. = 73102; 1: CHANGED COVERING EXT 73102` ### changcom Change subscriber community ID #### Syntax ####
> changcom [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies subscriber community IDs in the current database of the voice mail system. Use the name, extension, and new community ID as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or extension does not belong to a valid system subscriber, an error message displays on the screen. If more records exist, database modification continues. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension | K | 10
> | new community id | C | 2
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE COMMUNITY ID ROUTINE` (<ADAP version name>) `name___________; extension = ________; new community id = _____; ____: CHANGED COMMUNITY ID__________` #### Example The following command modifies one subscriber in the subscriber database. changcom -i "Doe, John","73101","3" The following data appears on the screen: `CHANGE COMMUNITY ID ROUTINE` (<ADAP version name>) `"Doe, John","73101","3" name = Doe, John; extension = 73101; new community id = 3; 5: CHANGED COMMUNITY ID 3` ### changcos Change subscriber class of service #### Syntax ####
> changcos [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies subscriber classes of service in the current database of the voice mail system. Use the name, extension, and new class of service as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. #### Input Format The Input formatInput format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension | K | 10
> | new class of service | C | 8
> You may use the value custom for the class of service. The subscriber's current class of service parameters are retained, but the subscriber's class of service is not associated with the original (or any) class of service thereafter (i.e. if the original class of service changes, the subscriber's attributes do not change). #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE COS ROUTINE` (<ADAP version name>) `name = __________; extension = ________; new cos = _______; ____: CHANGED COS__________` #### Example The following command modifies one subscriber in the subscriber database. changcos -i "Brown, Jane", "73101", "3" The following data appears on the screen: `CHANGE COS ROUTINE` (<ADAP version name>) `"Brown, Jane","73101","3" name = Brown, Jane; extension = 73101; new cos = 3;` `1: CHANGED COS 3` ### changext Change subscriber extension #### Syntax
> changext [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies subscriber extensions in the current database of the voice mail system. Use the name, old extension, and new extension as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or old extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. Since no duplicates for extensions are allowed, make sure you order the file correctly. #### Input Format The Input format consists of one record for each subscriber formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> --- | --- | --- | ---
> | name | C | 29
> | old extension | K | 10
> | new extension | K | 10
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE EXTENSION ROUTINE` (<ADAP version name>) `name = __________; extension = ________; new extension = _____; ____: CHANGED EXT__________` #### Example The following command modifies one subscriber in the subscriber database. changext -i "Doe, John","73101","73199" The following data appears on the screen: `CHANGE EXTENSION ROUTINE` (<ADAP version name>) `"Doe, John","73101","73199" name = Doe, John; extension = 73101; new extension = 73199;` `1: CHANGED EXT 73199 (NEW) NEWLINE` ### changmis Change subscriber miscellaneous field #### Syntax ####
> changmis [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies subscriber miscellaneous fields in the current database of the voice mail system. Use the name, extension, and miscellaneous fields for each subscriber as input. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension | K | 10
> | new misc 1 | C | 11
> | new misc 2 | C | 11
> | new misc 3 | C | 11
> | new misc 4 | C | 11
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE MISCELLANEOUS ROUTINE` (<ADAP version name>) `name = _________; extension = ________; new misc 1 = ______; new misc 2 = _______; new misc 3 = _______; new misc 4 = _______; ____: CHANGED MISCELLANEOUS__________` #### Example The following command modifies one subscriber in the subscriber database. changmis -i "Green, Sarah", "73101", "N45j2", "misc 2", "misc 3", "misc 4" The following data appears on the screen: `CHANGE MISCELLANEOUS ROUTINE` (<ADAP version name>) `"Green, Sarah","73101","N45j2","misc 2","misc 3","misc 4" name = Green, Sarah; extension = 73101; new misc 1 = N45j2; new misc 2 = misc 2; new misc 3 = misc 3; new misc 4 = misc 4;` `1: CHANGED MISCELLANEOUS N45j2` With the ADAP only one miscellaneous field is available. So, in order to set that field, the input file should contain one or more lines similar to the following: "name","extension","misc" Also, in order to clear the miscellaneous field, the input file should contain one or more lines similar to the following: "name","extension","" With the ADAP5.0 (and beyond) software, two cases are possible: For the first case, in order to set the miscellaneous field, the input file should contain one or more lines similar to the following: "name","extension","misc","","","" Also, in order to clear the miscellaneous field, the input file should contain one or more lines similar to the following: "name","extension","","","","" For the second case, in order to set any or all of the four miscellaneous fields, the input file should contain one or more lines similar to the following: "name","extension","misc1","misc2","misc3","misc4" Also, in order to clear all four of the miscellaneous fields, the input file should contain one or more lines similar to the following: "name","extension","","","","" Finally, in order to set some of the miscellaneous fields and clear others, the input file should contain one or more lines similar to the following: "name","extension","misc1","","misc3","" ### changmsg Change subscriber priority message #### Syntax ####
> changmsg [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies the subscriber priority message field in the current database of the voice mail system. Use the name, extension, and y or n as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. #### Input Format The Input format consists of one record for each subscriber.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension | K | 10
> | priority message indicator | L | 1
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE PRIORITY MESSAGE ROUTINE` (<ADAP version name>) `name = ________; extension = _______; new priority message indicator = _______; ____: CHANGED PRIORITY MESSAGE__________` #### Example The following command modifies one subscriber in the subscriber database. changmsg -i "Doe, John","73101","n" The following data appears on the screen: `CHANGE PRIORITY MESSAGE ROUTINE` (<ADAP version name>) `"Doe, John","73101","n" name = Doe, John; extension = 73101; new priority message indicator = n; 1: CHANGED PRIORITY MESSAGE` ### changnam Change subscriber name #### Syntax ####
> changnam [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies subscriber names in the current database of the voice mail system. Use the name, extension, and new name as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the old name and/or extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | old name | C | 29
> | extension | K | 10
> | new name | C | 29
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE SUBSCRIBER NAME ROUTINE` (<ADAP version name>) `name = _________; extension = ________; new name = _______________; ____: CHANGED NAME__________` #### Example The following command modifies one subscriber in the subscriber database. changnam -i "Doe, Mary", "73101", "Smith, Mary" The following data appears on the screen: `CHANGE SUBSCRIBER NAME ROUTINE` (<ADAP version name>) `"Doe, Mary","73101","Smith, Mary" name = Doe, Mary; extension = 73101; new name = Smith, Mary;` `1: CHANGED NAME Smith, Mary` ### changpwd Change subscriber password #### Syntax ####
> changpwd [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies subscriber passwords in the current database of the voice mail system. Use the name, extension, and new password as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or extension doesn't belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension | K | 10
> | new password | C | 15
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE PASSWORD ROUTINE` (<ADAP version name>) `name = _________; extension = ________; new password = _______; ____: CHANGED PASSWORD__________` #### Example The following command modifies one subscriber in the subscriber database. changpwd -i "Doe, John", "73101", "565656" The following data appears on the screen: `CHANGE PASSWORD ROUTINE` (<ADAP version name>) `"Doe, John","73101","565656" name = Doe, John; extension = 73101; new password = 565656;` `1: CHANGED PASSWORD 565656` ### changsub Change subscriber attributes #### Syntax ####
> changsub [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### This command modifies subscriber attributes in the current database of the INTUITY AUDIX. Use the subscriber attributes in the order described in this manual page as input for each subscriber. The subscriber must exist on the voice mail machine before using this command. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or extension does not belong to a valid system subscriber, an error message displays. If more records exist in the input file (<ifile) or typed in interactively (-i), database modification continues. #### Input Format The Input format consists of one record for each subscriber. One record is to be placed per line when using the input file. All input fields must be enclosed in a pair of double quotation marks ("") and separated by commas.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension | K | 10
> | [class of service] | C | 8
> | [password] | C | 15
> | [switch number] | N | 2
> | [miscellaneous] | C | 11
> | [covering extension] | K | 10
> | [addressing format] | C | 9
> | [CA permissions] | C | 14
> | [announcement control] | C | 1
> | [outcalling] | L | 1
> | [text service machine] | C | 10
> | [user id] | C | 30
> | [incoming mailbox LIFO/FIFO] | C | 4
> | [incoming mailbox order] | C | 3
> | [new retention time] | N | 3
> | [old retention time] | N | 3
> | [unopened retention time] | N | 3
> | [outgoing mailbox LIFO/FIFO] | C | 4
> | [outgoing mailbox order] | C | 5
> | [file cabinet retention time] | N | 3
> | [del/non del retention time] | N | 3
> | [max VM message length] | N | 4
> | [min VM space needed] | N | 4
> | [max CA message length] | N | 4
> | [min CA space needed] | N | 4
> | [max number of mailing lists] | N | 3
> | [max total mailing list entries] | N | 5
> | [max mailbox size] | N | 5
> | [guaranteed space] | N | 4
> | [new subscriber name] | C | 29
> | [new extension] | K | 10
> | [locked] | L | 1
> | [community id] | N | 2
> | [broadcast mailbox] | L | 1
> | [priority messages] | L | 1
> | [broadcast permissions] | C | 5
> | [end of message warning time] | N | 2
> | [ca language choice] | L | 1
> | [login announcement set] | C | 14
> | [ca primary announcement set] | C | 14
> | [ca secondary announcement set] | C | 14
> | [IMAPI access] | L | 1
> | [IMAPI voice file/message transfer] | L | 1
> | [secondary extension] | K | 10
> | [FAX creation] | L | 1
> | [trusted server access] | L | 1
> You can leave any of the fields unaltered by placing between the comma delimiters a successive pair of double quotes. To erase a field, place into the input record a string of spaces equal in size to the width of the field. (For example, to blank the contents of the Miscellaneous field, place a string of 11 space characters enclosed in double quotes into the input record.) To change a subscriber's name, place the old name into the Subscriber Name field and the new name into the New Subscriber Name field. After the changsub operation, the subscriber is then keyed by the new name. The next time getsub is employed to retrieve subscriber information, the new name appears as the first field in the output record. To change a subscriber's extension, place the old extension into the Extension field and the new extension into the New Extension field. After the changsub operation, the subscriber is then keyed by the new extension. The next time getsub is employed to retrieve subscriber information, the new extension appears as the second field in the output record. The value for Class of Service may be the name or number of any class of service known to the voice mail machine, including custom. The ADAP command does not verify input for data correctness, a task performed on the AUDIX side of the connection. However, it passes along any error messages it receives from the AUDIX System. The following table is a guide for input to fields that do not simply accept text or numbers up to a particular limit, nor are yes/no activations:
> Field description | Acceptable values for INTUITY AUDIX Systems
> CA permissions | auto-attendant, bulletin-board, call-answer, or none
> incoming mailbox lifo/fifo | lifo or fifo
> incoming mailbox order | the letters n, u, and o, in any order
> outgoing mailbox lifo/fifo | lifo or fifo
> outgoing mailbox order | the letters f, u, n, d, and a, in any order
> broadcast permissions | voice, login, both or none
> #### Output Format The items described in this section are directed to standard output. The location of any newline characters in the output is unpredictable. Upon start-up, the program prints a header declaring the function and version of the program: `SUBSCRIBER CHANGE ROUTINE` (<ADAP version name>) If the program is successful in parsing the input record, it echoes the values it sees for each of the fields. In interacting with all voice mail releases, the output for each input record consists of the command statistics as follows: `name = _________; extension = ____; cos = _______; password = _____; switch number = __; misc = _______; covering ext = _____; addressing format = _; CA permissions = _; announcement ctrl = _; outcalling = _; text service machine = ______; user id = ________________; incoming lifo/fifo = _; incoming category order = ___; new retention time = ____; old retention time = ____; unopened retention time = ____; outgoing lifo/fifo = _; outgoing category order = ____; file cabinet retention time = ____; del/nondel retention time = ____; max VM message length = ____; min VM space needed = ____; max CA message length = ____; min CA space needed = ____; max mailing lists = ____; max total list entries = _____; max mailbox size = ____; min guaranteed space = ____; new name = __________; new extension = ____; locked = _; community id = ___; broadcast mailbox = _; priority msgs = _; broadcast permissions = _; warning time = _;` The INTUITY AUDIX System includes the following additional items: `CA language choice = _; login annc set = ________ ; CA primary annc set = _____; CA secondary annc set = ______ ; IMAPI access = _____; IMAPI message transfer = ________; secondary extension = ______; FAX creation = __; trusted server access = __;` Next, the program relays the input record to the voice mail machine and attempts the change operation. If the transaction with the voice mail machine was not successful, the program passes along the error message received from the voice mail system. If the transaction was successful, the output shows (reflecting new extension, if changed): `___: CHANGED EXT __________` The first blank of the above is replaced with the line number of the processed input record. The second blank holds the extension number of the subscriber modified. If the string CHANGED EXT followed by a space and the desired extension does not appear in the output, the operation has failed. Upon termination, the program prints a summary of the number of subscribers successfully modified: `<n> subscribers changed` If the number printed does not match the number of input records, one or more of the requested change operations has failed. ### changsw Change subscriber switch number #### Syntax ####
> changsw [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies subscriber switch numbers in the current database of the voice mail system. Use the name, extension, and new switch number for each subscriber as input. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> 1 | name | C | 29
> 2 | extension | K | 10
> 3 | new switch number | N | 2
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE SWITCH ROUTINE` (<ADAP version name>) `name = _________; extension = _______; new switch number = _______; ____: CHANGED SWITCH__________` #### Example The following command modifies one subscriber in the subscriber database. ### chgrcom Change remote subscriber community ID #### Syntax ####
> chgrcom [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies remote subscriber community IDs in the current database of the voice mail system. Use the name, extension, and new community ID for each subscriber as input. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information #### Errors If the name and/or extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continue. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> 1 | name | C | 29
> 2 | extension/text address | C | 64
> 3 | new community id | N | 2
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE REMOTE COMMUNITY ID ROUTINE` (<ADAP version name>)`name = _________; extension/text address = _______; new community id = __; ___: CHANGED COMMUNITY ID__________` #### Example The following command modifies one remote subscriber in the subscriber database. chgrcom -i "Smith, David", "74101", "3" The following data appears on the screen: `CHANGE REMOTE COMMUNITY ID ROUTINE` (<ADAP version name>) `"Smith, David","74101","3" name = Smith, David; extension/text address = 74101; new community id = 3;` `1: CHANGED COMMUNITY ID 3` ### chgrext Change remote subscriber extensions #### Syntax ####
> chgrext [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies remote subscriber extensions in the current database of the voice mail system. Use the name, old extension, and new extension for each subscriber as input. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or old extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. Since no duplicates for extensions are allowed, make sure you order the file correctly. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> 1 | name | C | 29
> 2 | old extension | K | 10
> 3 | new extension | K | 10
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE REMOTE EXTENSION ROUTINE` (<ADAP version name>) `name = _________; extension = _______; new extension = _________; ____: CHANGED EXTENSION__________` #### Example The following command modifies one remote subscriber in the subscriber database. chgrext -i "Smith, Alice", "74101", "74229" The following data appears on the screen: `CHANGE REMOTE EXTENSION ROUTINE` (<ADAP version name>) `"Smith, Alice","74101","74299" name = Smith, Alice; extension = 74101; new extension = 74299;` `1: CHANGED EXT 74299` ### chgrmach Change remote subscriber machines #### Syntax ####
> chgrmach [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies the remote subscriber system (machine) (and optionally the extension) in the current database of the voice mail system. Use the name, extension, machine, and new extension as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. #### Input Format The Input format consists of one record for each subscriber, formatted as follows. The "new extension" portion of the input is optional.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> | name | C | 29
> | extension | K | 10
> | new machine | C | 10
> | [new extension] | K | 10
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE REMOTE MACHINE ROUTINE` (<ADAP version name>) `name = ________; extension = ______; new machine = _____; new extension = _____; ____: CHANGED MACHINE__________` #### Example The following command modifies one remote subscriber in the subscriber database. chgrmach -i "James, Jan", "74199", "omaha","76199" The following data appears on the screen: `CHANGE REMOTE MACHINE ROUTINE` (<ADAP version name>) `"James, Jan","74199","omaha","76199" name = James, Jan; extension = 74199; new machine = omaha; new extension = 76199;` `1: CHANGED MACHINE omaha` ### chgrnam Change remote subscriber names #### Syntax ####
> chgrnam [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command modifies remote subscriber names in the current database of the voice mail system. Use the name, extension, and new name as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the old name and/or extension does not belong to a valid system subscriber, an error message displays. If more records exist, database modification continues. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> 1 | old name | C | 29
> 2 | extension/text address | C | 64
> 3 | new name | C | 29
> #### Output Format The Output format for each record consists of the command statistics as follows: `CHANGE REMOTE SUBSCRIBER NAME ROUTINE` (<ADAP version name>) `name = _____________; extension/text address = ___________; new name = ___________________; __: CHANGED NAME___________` #### Example The following command modifies one remote subscriber in the subscriber database. chgrnam -i "Hobbs, Ellen","74199","Smith, Ellen" The following data appears on the screen: `CHANGE REMOTE SUBSCRIBER NAME ROUTINE` (<ADAP version name>) `"Hobbs, Ellen","74199","Smith, Ellen" name = Hobbs, Ellen; extension/text address = 74199; new name = Smith, Ellen;` `1: CHANGED NAME Smith, Ellen` ### delrsub Delete remote subscribers #### Syntax ####
> delrsub [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command deletes remote subscribers from the current database of the voice mail system. Use the name and extension as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or extension does not belong to a valid voice mail system remote subscriber, an error message displays. If more records exist, subscriber deletion continues. #### Input Format The Input format consists of one record for each subscriber, formatted as follows:
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> 1 | name | C | 29
> 2 | extension/text address | C | 64
> #### Output Format The Output format for each record consists of the command statistics as follows: `REMOTE SUBSCRIBER DELETE ROUTINE` (<ADAP version name>) `name = _________; extension/text address = _______; ____: DELETED SUB_________` #### Example The following command deletes one remote subscriber in the subscriber database. delrsub -i "Mary 74199","76199" "Jones, James","76199" The following data appears on the screen: `REMOTE SUBSCRIBER DELETE ROUTINE (<ADAP version name>) "Jones, James","76199" name = Jones, James; extension/text address = 76199; 1: DELETED SUB 76199` ### delsub Delete subscriber #### Syntax ####
> delsub [-r release] [-v] [-w] [-V] [-i] [< ifile] [> ofile]
> #### Description This command deletes subscribers from the current database of the voice mail system. Use the name and extension as input for each subscriber. Command statistics are written to standard output. See the Command Line Database Modification Description Table for more information. #### Errors If the name and/or extension does not belong to a valid system subscriber, an error message displays. If more records exist, subscriber deletion continues. #### Input Format The Input format consists of one record for each subscriber, formatted as follows.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> 1 | name | C | 29
> 2 | extension | K | 10
> When connected to an AUDIX system, only as many characters are required in the name field as needed to make the name unique. #### Output Format The Output format for each record consists of the command statistics as follows: `SUBSCRIBER DELETE ROUTINE` (<ADAP version name>) `name = _________; extension = _______; ____: DELETED EXT_________` ### setalogp Set activity log parameters #### Syntax ####
> setalogp [-a y/n] [-M y/n] [-N nnnn] [-c y/n] [-r release] [-v] [-w] [-V]
> - #### Description This command sets the field values for the following screens. INTUITY AUDIX Change System-Parameters Activity-Logsn
>   -a | Activity log flag; must be followed by y or n.
>   y/n | Activates or deactivates the activity log.
>   -M | Message waiting indicator (MWI)flag; must be followed by y or n.
>   y/n | Records or does not record MWIs.
>   -N | New max. number of activity log entries flag; must be followed by nnnn.
>   nnnn | The maximum number of activity log entries. If this number is smaller than the previous maximum number of entries, the activity log is cleared.
>   -c | Clear activity log flag; must be followed by y or n.
>   y/n | Clears or does not clear the activity log. Defaults to n.
>   -r | Release flag; must be followed by release.
>   release | Sends data for the specified release of the INTUITY AUDIX.
>   -v | Writes transfer statistics to the screen at the end of the transfer. Pressing v while the command is executing displays the updated transfer status.
>   -w | Writes a one-line summary of the exit status of this command into the file, form_req.rc.
>   -V | Writes the ADAP version number for this command and exits without transferring any screens data.
> > #### Example The following command sets the field values of the Change System-Parameters Activity-Log screen data and writes a summary of the transfer statistics to the screen: setalogp -a y -N 500 -v ##### Command Line Database Modification Description Table
> > -r | Release flag; must be followed by the release.
> > release | Sets the data for the specified release of the software.
> > -v | Writes transfer statistics to the screen at the end of the transfer. Unless -i is specified, pressing v while the command is executing sends the updated transfer status to the screen.
> > -w | Writes a one-line summary of the exit status of this command into the file, main.rc.
> > -V | Writes the ADAP version number for this command and exits without transferring any screens data.
> > -i | Turns on interactive data input mode. Turns off the search for possible subsequent entry of the v (verbose) and q (quit) options. If you don't specify -i, you must specify an input file (< ifile) from which the names, extensions, etc., will be read.
> > < ifile | Name of an input file you have created. The filename must be preceded by the symbol <.
> > | This file contains one or more subscriber records to be modified. Each record includes the attributes of the subscriber to be added. You can edit the output of the getlist command to generate input to this command. If you don't specify an input file, you must type the subscriber attributes directly from your keyboard after entering this command.
> > > ofile | Specifies the file to which command statistics are to be written.
Top of page

| Search This CD Index Contact Us
| © 2002-2007 Avaya Inc. All rights reserved.